|
|
Controllers Configuration |
Controllers provide audiovisual feedback on the access decision. Typically, a red/green light (LED) indicator on the reader informs the cardholder that the door is unlocked or that access has been denied. A local door alarm can be installed to provide an audible warning if the door is forced open or remains open after an access.
The controller
definition tells the system how a controller is being used and what devices
are associated with it: (doors, input zones, relays and output devices).
| Type | Door(s) | Wireless Doors (licensed) | Relays | Input Zones | Auxiliary Outputs |
|---|---|---|---|---|---|
| KT-100 | 1 | not supported | 4 | 4 | 2 |
| KT-200 | 2 | not supported | 2 | 16 | 4 |
| KT-300 | 2 | not supported | 2 | 8 | 4 |
| KT-400 | 4 | 8 | 4 | 16 | 16 |
| KT-1 | 1 | 2 | 2 | 5 | 5 |
To find a list of modules communicating with a controller but unassigned, click the Request Unassigned Modules icon. A window with the following information displays:
Module Type: ioSmart or ioModule.
Module Serial Number: of the module.
To define an unassigned module, right-click the module, and click Assign module, it automatically populates the module’s data into the controller’s configuration page in the ioModule tab, or the ioSmart tab. If required, rename the module, or change the configuration details, and click Save. When you define the module, the system removes it from the list.
1 - From the Devices/Controller window, select a Site filter from the first drop-down list.
2 - Select the Gateway (please refer to Gateway Configuration for more details about configuring a gateway) .
3 - From the Connection drop-down list, select the connection where the controller is located (please refer to Connection Configuration for more details about configuring a connection) .
4 - From the Controller drop-down list, select the controller you want to define. Once selected, the language section is enabled. You may rename the selected controller.
5 - From the KT controller type drop-down list, select a controller type. Once selected, the language section is enabled. You may rename the selected controller.
• Assign a meaningful name to the controller in the language section (English and French in our example), then click the Save button. Once you save, the Controller type drop-down list becomes disabled.
• The system prompts you to use the Express Setup program. Click Yes to continue. If you select No you will have to manually configure these devices in their respective definition menus (doors, relays, inputs and auxiliary outputs).
EntraPass offers you the ability to install two types of readers on the same controller
(primary and secondary). This feature is only available
On a given controller, all reader types must be the same (Wiegand or ABA).
6 - Select the reader installed on your controller from the Reader type drop-down lists. Check Table 1 for the reader types versus the controller type.
The
button
allows you to install a custom driver for a specific controller. Moreover,
using this button allows you to add the driver in the Reader+ Driver table,
making it available the next time you want to configure a new controller.
| Reader Types | KT-100 | KT-200 | KT-300 | KT-400/KT-1 |
|---|---|---|---|---|
| ABA with Type CNPID Cards | Yes | Yes | Yes | |
| BC-201 - CF100 | Yes | Yes | Yes | |
| BC-201 Bar code with Polaris Cards | Yes | Yes | Yes | Yes |
| CARDKEY | Yes | Yes | Yes | |
| CASI-RUSCO 26/28-Bit Wiegand | Yes | Yes | Yes | |
| CHECKPOINT Sielox Format | Yes | Yes | Yes | |
| CHUBB | Yes | Yes | Yes | |
| DORADO ABA clock and data | Yes | Yes | Yes | |
| DORADO ABA Wiegand | Yes | Yes | Yes | |
| DORADO EMPI 26-Bit | Yes |
|
Yes | |
| DORADO EMPI 34-Bit | Yes | Yes | Yes | |
| FIPS 201 75-bit no expiry date | Yes | |||
| FIPS 201 75-bit with expiry date | Yes | |||
| h20302, 37-Bit | Yes | Yes | Yes | Yes |
| HID CORPORATE 1000 Generic | Yes | Yes | Yes | Yes |
| HID iClass 37-Bit No Party | Yes | |||
| HID KSF (Kantech Secure Format) | Yes | Yes | Yes | Yes |
| HUGHES 36-Bit - CF104 | Yes | Yes | Yes | |
| INDALA old 27-Bit Format | Yes | Yes | Yes | |
| INTERCON | Yes | Yes | Yes | |
| ioProx Dual Driver (26-Bit and XSF) | Yes | Yes | Yes | Yes |
| ioProx Kantech 26-Bit Wiegand | Yes | Yes | Yes | Yes |
| ioProx Kantech XSF Format | Yes | Yes | Yes | Yes |
| ioProx UK 31-Bit Wiegand | Yes | |||
| ioSmart Kantech SSF Format (Wiegand) | Yes | Yes | Yes | Yes |
| ioSmart Kantech SSF Format (RS-485) | Yes | |||
| KRONOS Card with Bar Code Reader | Yes | Yes | Yes | |
| Mifare 32-Bit CSN | Yes | Yes | Yes | Yes |
| Mifare 34-Bit AID 517A | Yes | Yes | Yes | |
| Mirage 135 | Yes | Yes | Yes | |
| NCS | Yes | Yes | Yes | |
| Northern 32-Bit with NR1 Reader | Yes | Yes | Yes | |
| Northern 34-Bit with Hughes Reader | Yes | Yes | Yes | |
| Paramount Farm 32-Bit Wiegand | Yes | Yes | Yes | Yes |
| Polaris 1 - CF101 | Yes | Yes | Yes | |
| Polaris 1 with 10-Digit Cards | Yes | Yes | Yes | |
| Polaris 1 with 16-Digit Cards | Yes | Yes | Yes | |
| Polaris 1 with Polaris Cards | Yes | Yes | Yes | Yes |
| Polaris 2 ABA with 10-Digit Cards | Yes | Yes | Yes | |
| Polaris 2 ABA with 16-Digit Cards | Yes | Yes | Yes | |
| Polaris 2 ABA with Polaris Cards | Yes | Yes | Yes | Yes |
| Polaris 2KP ABA with 10-Digit Cards | Yes | Yes | Yes | |
| Polaris 2KP ABA with 16-Digit Cards | Yes | Yes | Yes | |
| Polaris 2KP ABA with Polaris Cards | Yes | Yes | Yes | Yes |
| Polaris 32/35/37 CHRS - CF103 | Yes | Yes | Yes | |
| RBH 50-Bit Card Driver | Yes | |||
| SCHLAGE 1030 and 1040 Card Format | Yes | Yes | Yes | |
| Sensor 26-Bit Wiegand Standard | Yes | Yes | Yes | Yes |
| Sensor 34-Bit Wiegand | Yes | Yes | Yes | Yes |
| SFT-R50 26-Bit | Yes | Yes | Yes | |
| Shadow PROX | Yes | Yes | Yes | Yes |
| Siteguard Format | Yes | Yes | Yes | |
| Wiegand 26/28-Bit - CF102 | Yes | Yes | Yes | |
| WLS Wireless 26-Bit | Yes | Yes | Yes | |
| WLS Wireless Shadow Prox and HID | Yes | Yes | Yes |
7 - Select the keypad installed on your controller from the Keypad type drop-down list. Check Table 2 for the keypad types versus the controller type.
| Keypad Types | KT-100 | KT-200 | KT-300 | KT-400/KT-1 |
|---|---|---|---|---|
| KP-1003H | Yes | Yes | Yes | |
| KP-500, KP-2000, KP-2500, KP-3000 | Yes | Yes | Yes | |
| ioProx with Integrated Keypad (8-Bit Burst) | Yes | Yes | Yes | Yes |
| POL-2KP - 5-Digit Integrated Keypad | Yes | Yes | Yes | Yes |
8 - Use the Disable controller polling when you need to put the controller in disable mode. In disable mode, the controller will never be polled and all status requests from this specific controller will send a message that this controller is disabled.
This option can be used when a controller is removed temporarily but must not be deleted (when under repair, for example). It also allows operators to easily setup the software before the physical installation is completed.
9 - Select the Vital LED mode (for KT-1 only). Please refer to KT-1 Installation manual D29008966 for details.
10 - Select between On demand and Always on for the Status LED (for KT-1 only) . Please refer to KT-1 Installation manual D29008966 for details.
11 - Select a Graphic and Video view to which the gateway is assigned, if applicable. The video view will only be activated If the video feature is enabled in EntraPass.
Controller types can be updated to newer controllers without resetting the controller configuration. To change the controller type do the following:
1 - From the Devices tab select Controller, then select a Controller from the drop-down list.
2 - Select a new controller type from the KT controller type drop down list.
3 - Click the save button. A warning message asks if you want to continue. Press Yes to continue. This launches the Express Setup window.
4 - Any undefined components can be configured using the Express Setup window. For example when changing from a KT-1 to a KT-400, the undefined doors can be configured.
5 - Click OK to complete the process.
6 - During the process the option Disable controller polling is automatically checked. Ensure that this option is unchecked
This function only supports updating controllers to newer controllers. The rules for updating controller types are summarized in the following table.
| Original controller type | Supported update controller types |
|---|---|
| KT-100 | KT-300, KT-1, KT-400 |
| KT-200 | KT-300, KT-400 |
| KT-300 | KT-400 |
| KT-1 | KT-400 |
When converting from KT-100 or KT-1 to KT-400 exit readers are converted to a second door.
It is not possible to change the controller type if a KT-IP has been used.
Combus and SPI modules associated with a controller cannot be transferred. To change the controller type, definitions for combus and SPI modules must first be removed.
1 - Select the controller tab (KT-100, KT-200, KT-300, KT-400 or KT-1) from the Controller window.
2 - Enter the controller serial number in the Serial number field. Usually, the number is found on the controller label. The field is defined to accept only numeric characters, except for the first character which may be an a or A . If a lower case character is entered, the system converts it to a capital letter.
3 - For KT-400 only:
• To configure SPI modules, please refer to Expansion Modules Setup.
• To configure the elevator floor associations, please refer to Defining the KT-400 Elevator Floor Associations.
4 - For KT-300 only:
• To configure Combus Modules, please refer to KT-300 Combus Modules.
• To configure the elevator floor associations, please refer to Defining the KT-300 Elevator Floor Associations.
5 - For KT-200 only:
• To configure KT-200 Auxiliary devices , please refer to Configuring KT-200 Auxiliary Devices.
• To define REB-8 relays, please refer to Defining REB-8 Relays.
• To configure REB-8 elevator controllers, please refer to Programming REB-8 Elevator Controllers.
• To configure KT-2252 elevator controllers, please refer to Programming KT-2252 Elevator Controllers.
6 - Enter the Wait for second access card delay. The maximum time allowed is 2 minutes and 7 seconds. This feature is useful for secured areas where two cards are required to access a secured door. If the value entered is greater than the maximum allowed, the system will use the existing value.
7 - In the Keypad escape key drop-down list, choose a keypad escape key if applicable. This feature is associated with PIN numbers. When a user enters a wrong number, he/she may press the escape key and re-enter the PIN, without incrementing the number of attempts.
8 - In the EOL resistor (5.6K) drop-down list, select the resistor type used with your system. By default, this choice is set to None . This feature is used as a supervision device for all inputs. In fact, if this feature is enabled and if an input is disconnected, an alarm message is generated and sent to the Alarm message desktop (or other desktop configured to receive such events).
9 - Select a value from the RS-485 baud rate list.
10 - In the Reader template list, click the more options button to select a reader template. Selecting a template ensures any reader connected to the controller inherits the template properties.
11 - Click the Save button.
Select
the
Status
relay
tab
to program a relay or group of relays that will be activated when an event
occurs. Click the
button to select a relay or a group of relays (not available for KT-100).
The Licensed Door feature must be installed prior to use. See System Registration for details.
The licensed wireless door feature supports the addition of Assa Abloy wireless doors in EntraPass. For more information about configuring the Assa Abloy interface, refer to the Application Note, ASSA ABLOY Wireless Locks integration (AH30 hub, serial). To configure your EntraPass installation for licensed wireless doors do the following.
• From the Devices/Controller window, select the controller you want to configure. If the controller supports licensed wireless doors the licensed door icon will be available from the Controller menu bar.
• Select the Licensed doors symbol.
• If no integrated panel has previously been linked to that controller EntraPass will automatically create a new integrated panel.
• Select Configuration to open the Licensed Doors window. The number of Purchased licences and Available (remaining) licenses is displayed.
• To add a door select +.
• You must input a description of the door and the device address. The device address (EAC address) has been configured during the configuration of the wireless lock. For more information about configuring the Assa Abloy interface, refer to the Application Note, ASSA ABLOY Wireless Locks integration (AH30 hub, serial).
• Check the correct box to indicate whether the door has a contact (to indicate open or close) or a REX (Request To Exit) functionality.
• To delete a door select Delete followed by OK.
• If an integration panel has previously been linked to the selected controller the Licensed Doors window will be displayed. Here you can edit existing wireless doors.
• To view the status of the wireless lock select the wireless lock from the Operation/Integrated Panel. The icon will signify if the device is operational. To view details double-click on the device. The possible states are listed in the table.
| Parameter | Possible States |
|---|---|
| Door Number: |
|
| Tamper: |
|
| Device communication status : |
|
| Door side: |
|
| Handle State: |
|
| Key Cylinder State: |
|
| Lock State: |
|
| Door State: |
|
| Protocol version: | |
| Version Number: | |
| Vendor ID: | |
| Mac Address: | |
| Hub Mac Address: | |
| On abnormal behaviour: |
|
Licensed wireless doors can be identified by a blue icon. Wired doors have a green icon in EntraPass.
There are less configurable parameters for wireless doors when compared to wired doors. There are also some differences to the operation of wireless doors.
• Some manual features such as Arm Door, Disarm Door, Door contact back to schedule and Disable Door Contact are not available for wireless locks.
• Wireless locks will go into a sleep mode to conserve power. When you send a manual operation to these locks you must wake up the lock (by interacting with the lock) for the manual operation to be processed. This is also true of unlock schedules which require the lock to be woken up to operate correctly. To wake a lock you may need to swipe your card twice.
• On initial power up the Tamper State will be reported as Unknown until the lock cover has been opened.
• If a wireless hub looses power it will not retain the last status of it wireless locks.
• The buzzer and LED cannot be controlled through EntraPass.
• When switching the length of the pin code, the wireless lock must be configured through it's own interface.
• The current status of the lock is only updated on an event.
• The wireless lock cannot be operated when disconnected from the controller.
• The lock state refers to deadbolt of he lock. When the dead bolt is engaged the lock state becomes unknown.
• Currently only 26-bit drivers are supported for wireless locks.
If you select Devices / Integrated Panel...Print you can see the number of licensed doors associated with that integrated panel.
Currently, wireless licensed doors are only supported for KT-1 and KT-400 controllers.
The Option tab enables operators to configure such features as:
• Anti-passback (for synchronizing entry/exit readers)
• Duress function (for defining a panic button)
• Card count options (for specifying cards in an area), etc.
The anti-passback option works with entry/exit readers. It allows security administrators to keep track of the number of monitored cardholders in an area. It is local to each controller defined by corresponding entry/exit readers. A relay can be activated when the counter reaches the number of cards defined to be inside the area; the relay is disabled when the number of cards in the area goes below the specified number.
1 - From the Controller window, click the Option tab to define anti-passback, duress and card count options.
2 - Determine the Duress options . When a duress option is selected, you have to assign a duress key, that is a silent panic key.
• Duress on access granted : This option enables the duress key when access is granted.
• Duress on access denied : This option enables the duress key, even when access is denied.
3 - Select a duress key from the Keypad duress key drop-down list.
For added
security, you may select both options.
4 -
From the
Anti-passback
options
• None : The anti-passback option is disabled.
• Soft anti-passback : This option allows a cardholder to use an entry (or exit) reader more than once without using the corresponding exit (or entry) reader. Only an “ Access granted - Passback bad location ” event is sent to the Message desktop.
• Hard anti-passback : A card used at an entry reader will not be able to access the same entry reader again until it has used the corresponding exit reader. Only an “ Access denied - Passback bad location ” event is sent to the Message desktop.
• Controller local area: This selection enables the Controller local area tab. This option is only functional with the KT-400; the Controller Local Area tab will only appear with a KT-400 (please refer to Defining the KT-400 Controller Local Areas for more details).
5 - In the Forgive schedule section, click the three-dot button to set a schedule for resetting the anti-passback option on all other cards.
The Forgive Schedule section is enabled only when Soft anti-passback or Hard anti-passback item is selected.
6 - In the Miscellaneous section, indicate options for Enable fail-soft delay (10-255 s) . During a fail-soft mode, the controller operates in stand-alone mode, following a communication failure.
7 - Enter the 32-bit card family code (optional). You can locate this hexadecimal code on the access card.
8 - In the Card count options , use the up or down controls to set the maximum card number. The maximum card number allowed is 2,147,483,647. The system keeps track of the number of monitored cards that are in the monitored area and activates a relay when the count is reached. When users exit the area, the counter decrements and the relay will eventually reset when the count is smaller than the value defined.
9 -
You may
configure the system to
activate a single relay
or
a
group
of relays
when
the maximum count is reached. Click the
button to select the
relay or relay group that will be activated when the number is reached.
The Activate relay section is enabled only when Soft anti-passback or Hard anti-passback item is selected.
1 - Select a schedule for the Power supervision (not available for KT-1).
2 - Select a schedule for the Tamper switch (not available for KT-100 and KT-300).
Please refer to Schedules Definition for more details about schedule configuration.
1 - From the Controller definition window, select the KT-200 tab.
2 - In the Auxiliary devices section, select the type of devices used with KT-200 controller.
• Check the REB-8 relay option if REB-8 expansion boards are used as relays. Only 16 relays can be defined. If two REB-8 are added, the last two relays (the 17th and 18th relays) can be used to perform different actions. You have to specify the additional actions for the two relays in the Extra relay drop-down list.
• Check the KT-2252 elevator controller and REB-8 relay option if KT-2252 are used as elevator controllers and REB-8 are used as relays on the same door controller. A maximum of four KT-2252 can be connected to the controller.
• Check the REB-8 Elevator Controller option if REB-8 are used for elevator control. Up to four REB-8 can be used for elevator control.
When an elevator controller option is checked, an Elevator tab appears beside the KT-200 tab.
The Elevator tab allows you to specify which auxiliary devices are used with the KT-200 for elevator control and how they are used. Depending on the expansion board installed and on the option checked, the Elevator window displays the REB-8 Installed or KT-2252 Installed section.
1 - From the Controller definition window, select the KT-200 tab.
2 - In the Auxiliary devices section, select KT-2252 elevator controller , or KT-2252 elevator controller and REB-8 relay . The Elevator tab appears.
3 - To configure elevator controllers, select the Elevator tab. When KT-2252 elevator controllers are used, the Elevator mode section is enabled.
4 - In the Elevator mode section, check the appropriate number of floors. This indicates how the floors are controlled with the KT-2252.
• Select 16 Floors if there is one KT-2252 for two cabs sharing the same floors.
• Select 32 Floors if there is one KT-2252 per cab.
The Inputs column refers to the KT-2252 terminals. When floors have been defined (in the Floor menu), the Floors column contains the floors that are associated with the inputs.
• In the KT-2252 installed section, specify the number of KT-2252 installed. The options are cumulative. If for example the KT-2252 #3 option is checked, KT-2252 #1 & 2 have to be checked as well. The following table summarizes how KT-2252 elevator controllers are used:
| Number of Cabs | Number of Floors | Number of KT-2252 |
|---|---|---|
| 1 | 8 | 1 |
| 1 | 16 | 1 |
| 1 | 32 | 1 |
| 1 | 64 | 2 |
| 2 | 8 | 1 |
| 2 | 16 | 1 |
| 2 | 32 | 2 |
| 2 | 64 | 4 |
5 - In the Floors column, select the floors associated with KT-2252 controller terminals.
The Inputs column refers to the KT-2252 terminals. When floors have been defined (in the Floor menu), the Floors column contains the floors associated with the inputs.
REB-8 relay expansion boards may be used as a cost-efficient alternative for elevator control. With a REB-8 expansion board added to a KT-200, the software may control up to two elevator cabs per controller.
1 - In the KT-200 definition window, select the REB-8 elevator controller option. When the option is selected, an Elevator tab appears beside the KT-200 tab. The REB-8 definition section is only active when REB-8 are used as relays.
2 - Select the Elevator tab to configure the REB-8 elevator controllers. Up to four REB-8 elevator controllers are supported.
3 - Specify the number of REB-8 that are installed on the controller. The selection is cumulative. For example, if four REB-8 are installed, the first three checkboxes have to be checked also. The following table summarizes how REB-8 are assigned to floors and to elevator cabs.
| Number of REB-8 | Number of Floors | Number of Cabs |
|---|---|---|
| 1 | 1 to 8 | Cab 1 |
| 2 | 9 to 16 | Cab 1 |
| 3 | 1 to 8 | Cab 2 |
| 4 | 9 to 16 | Cab 2 |
Note...
The Inputs column refers to the REB-8 terminals. When floors have been defined (in the Floor menu), the Floors column contains the floors that are associated with the inputs.
4 - In the Floors column, select the floors associated with REB-8 controller terminals. For details on floor definition and door group definition, see Doors Configuration.
There is no floor confirmation when an REB-8 is used as an elevator controller.
When REB-8 are used as relays, you need to specify how many relays are installed on the KT-200. The controller can handle a maximum of 16 accessible relays and already provides 2 on-board relays.
1 - Under the KT-200 tab, select the REB-8 relay option if REB-8 are used as relays.
2 - If they are used with the KT-2252 elevator controller, select the KT-2252 elevator controller and REB-8 relay option. In either case, the REB-8 definition section is enabled.
3 - In the REB-8 Definition section, select the appropriate option: No REB-8, One REB-8 or Two REB-8.
4 - If two REB-8 are added (for a total of 18 relays), the last two relays can be used to perform different actions: select the use for the extra relays from the Extra relay drop-down list.
5 - Select the Status relay tab to program a relay or group of relays that will be activated when an event occurs.
The Elevator tab displays only when Combus modules have been defined as elevators under the KT-300 tab.
1 - In the Controller window, click the elevator tab to define the floor associations.
2 - From the Floors drop-down menu, for each number select a floor.
3 - Click Save .
To define floors, please refer to Floor Definition.
The KT-400 support expansion modules through its SPI expansion port. The SPI port is a 6-conductor cable bus to which several expansion modules are daisy-chained to add inputs, outputs and relays.
The KT-400 SPI port maximum current draw is 500 mA, when the 12V AUX terminals are not used. External power supply (12 VDC, 2 Amps) for the expansion module is required when the total current draw exceeds 500mA on the SPI Port. For additional hardware details, please refer to the KT-400) Installation Manual , DN1726.
Three expansion module types are available:
• KT-MOD-INP16 : The KT-MOD-INP16 is an input module that adds 240 zones to the KT-400 controller. Up to 15 input modules (16 input modules if used for elevator configuration) can be connected to a KT-400 for a total of 240 external inputs. Adding the 16 onboard inputs of the KT-400 gives a total of 256 inputs per KT-400. For further details, check the KT-MOD-INP16 KT-400 Expansion Module 16-Zone Input with SPI Cable, Install Sheet , DN1776.
• KT-MOD-OUT16: The KT-MOD-OUT16 is a 16-output module. It can be used for elevator access control with additional hardware. Up to 16 output modules can be connected to a KT-400 for a total of 256 outputs. For further details, check the KT-MOD-OUT16 KT-400 Expansion Module 16-Output with SPI Cable, Install Sheet , DN1781.
• KT-MOD-REL8: The KT-MOD-REL8 is an 8-relay outputs expansion module used as general relays or elevator control outputs. Up to 32 relay modules can be connected to a KT-400 for a total of 256 relays. For further details, check the KT-MOD-REL8 KT-400 Expansion Module 8-Relay Output with SPI Cable, Install Sheet , DN1786.
The following table summarizes the options associated with each module:
| Expansion Module | Options |
|---|---|
| KT-MOD-INP16 | Controller inputs (up to 256) and/or elevator inputs (up to 64 per elevator door) |
| KT-MOD-OUT16 | Outputs relays (up to 256) and/or elevator outputs (up to 64 per elevator door) |
| KT-MOD-REL8 ( Note ) | Relays (up to 256) and/or elevator outputs (up to 64 per elevator door) |
There are already 4 relays available on the KT-400. Make sure to check the relay number assignments to prevent redundancy unless it has been planned on purpose.
The 9-16 relay configuration is set by default.
1 - If an expansion module(s) is(are) connected to a KT-400, click the SPI module configuration button. The Expansion modules setup appears.
| If you want to | then go to |
|---|---|
| configure an input module KT-MOD-INP16 | Step 2. |
| configure an output module KT-MOD-OUT16 | Step 5. |
| configure an output module KT-MOD-REL8 | Step 6. |
| modify an existing expansion module configuration | Step 7. |
2 - To add a KT-MOD-INP16, select the Input Module tab and then click on Add . If there is more than one input modules listed, make sure that you select the correct one before changing the input assignments. Assign names to the modules in the language fields and choose the options.
3 - Select the DEOL: Double end-of-line resistor JP4 On checkbox to define a KT-MOD-INP16 module in DEOL.
The entire expansion board is used to provide 8 inputs with DEOL. These 8 inputs are added of the next group of 8 inputs. For example, if inputs #33-40 are linked to a DEOL module, inputs #33-40 and #41-48 will not be available for other modules.
Controller inputs 1-16 are reserved to the inputs on the KT-400.
4 - Selection of the inputs numbers can be done in two ways; using the drop-down menu or the Extended selection box. Right-click on the inputs menu selection to view the Extended selection box, see Using the Extended Selection Box
This is an exclusive condition. You cannot select the same item in the Inputs drop-down menu and in the Elevator inputs drop-down menu because it will be a duplicate, and the system does not accept any duplicate. For example, Inputs # 17-24 cannot be selected twice. Another way to let you understand this concept, is that in the Elevator inputs menu the same item will not be available for the same door. The same concept applies for the Elevator outputs menu.
5 - To add a KT-MOD-OUT16, select the Output Module tab and then click on Add . When you click on the Add button, a menu appears and lets you select which output module you want to add. Assign names to the modules in the language fields and choose the options.
6 - To add a KT-MOD-REL8, select the Output Module tab and then click on Add . When you click on the Add button, a menu appears and lets you select which output module you want to add. Assign names to the modules in the language fields and choose the options.
Warning: There are already 4 relays available on the KT-400. Make sure to check the relay number assignments to prevent redundancy unless it has been planned on purpose.
7 - From the Summary tab, you can modify all the modules. Make sure to highlight the module you want to modify in the left column before doing any modifications on the right side.
8 - When you have finished configuring the expansion modules, click the OK button to go back to the KT-400 configuration window.
For more information, Connection Configuration.
To define a KT-MOD-IO16 for a KT-400, or a KT-1 controller, click the ioModule tab, and complete the following steps:
1 - Select a controller from the Controller list, and click the ADD button.
2 - In the ioModule area, type the name of the ioModule in the language field.
3 - In the Serial Number field, type the serial number.
4 - Select one of the following terminal banks:
• Terminals 1 - 4
• Terminals 5 – 8
• Terminals 9 – 12
• Terminals 13 – 16
For each terminal select one of the following action options:
○ Not in use: this is the default setting. Select to indicate that terminals are not in use.
○ Use as input: select to use terminals of inputs/outputs as inputs. EntraPass uses the same setting for EOL as the controller settings. If you want to change EOL settings, use the Input menu. For more information see, Configuring Specific Controller Parameters in the Inputs field, select an input bank from the list.
You cannot use an input bank on multiple devices. When you use it on one device, it is no longer available, until you delete the configuration.
○ Use as relay: select to use terminals of inputs/outputs as relays. In the Relays field, select a relay bank from the list.
You can define a relay bank on multiple devices, they mirror each other.
○ Use as elevator: select to use terminals of inputs/outputs as elevator doors. Two further options become available:
• Use as outputs
• Use as floor confirmation (inputs)
Use as outputs
a - In the Elevator field, select an elevator from the list.
b - In the Elevator outputs field, select the elevator output bank from the list.
You can define an elevator output bank on multiple elevators they mirror each other.
Use as floor confirmation (inputs)
a - In the Elevator field, select an elevator from the list.
b - In the Elevator inputs field, select an elevator input from the list.
You cannot use an input bank on multiple devices. When you use it on one elevator, it is no longer available, until you delete the configuration.
Terminals 9 – 12
In addition to the Not in use, Use as input, Use as relay, and Use as elevator options, Use as SPI is available for Terminals 9 – 12.
Use as SPI: select to use terminals 9 – 12 as SPI relays. In addition to the 32 SPI relay modules defined directly in the SPI tab, you can add another 32 relay SPI modules using the ioModule tab.
To continue the configuration, complete the following steps:
a - Click the SPI tab, and click the Output module on ioModule tab.
b - If you have defined more than one ioModule, select the one you want from the ioModule list.
c - In the Relay 1 - 8 tab, select one of the following options:
• Not used
• Used as relays
• Use as elevator equipment
You can define relays on the SPI expansion module, and on the ioModule. For example, for the KT-1 controller, if you define relays 1 - 4 on an ioModule, and an SPI expansion module, it lights up on the controller, the ioModule, and the SPI expansion module.
5 - To remove a module, click the REMOVE button.
This feature is to bring up the number of readers to 8 (on 4 doors) for KT-400 and KT-401 controllers (only) when using ioProx XSF or IoProx UK 31 bits readers. This way, a second reader can be connected to the controller. That second reader will keep the same values as the first one for:
• Door lock mode
• Unlock time
• Open time
• Extended Unlock time
• Extended Open time
• Unlock Schedule
• Video View
• Graphic
• All “Door Contact” features
• Relay Activation for Door events except “Door forced open”
The second door will automatically be labelled with the first door name plus the word EXIT at the end.
1 - From the KT-400 tab, under Enable exit reader, select the doors for which the reader has to be enabled.
2 - Click Save .
• The feature is available only when IoProx XSF or IoProx UK 31-Bit readers are used under General/Reader and keypad. If another type of reader is selected, the option is not available.
• A number of option fields are not available for the 2nd reader since values are already programmed in the first one.
• If you deselect the exit reader under controller, the exit reader will be disabled. It is not possible to DELETE an exit reader.
The
controller local area
option is only available with a KT-400 controller
1 - Click the Controller local area tab to define up to 4 local areas.
2 - Assign a name for both languages for the 1st controller local area.
3 - Select the Forgive schedule from the drop-down menu.
4 - Enter the maximum number of cards allowed in the Cards threshold field.
5 - Check the Deny access on area full box to prevent more users to enter the area after the cards threshold has been reached.
6 - Click on the three-dot to select the relay or the relay group to activate when the cards threshold has been reached.
7 - Repeat steps 2 to 6 for each controller local area.
The Elevator tab displays only when expansion modules have been defined as inputs or outputs for elevators under the KT-400 tab.
For KT-400 controller, it is possible to choose up to four patterns to define door and floor numbers that will be associated with each pattern. By default, pattern 1 specifies all door numbers.
1 - In the Controller window, click the elevator tab to define the floor associations.
2 - In the Elevator tab, click Pattern #2 , and then select the appropriate Door number check box(es).
3 - From the Floors drop-down menu, select the appropriate item or floor number to associate with the door number and the pattern number.
4 - Repeat Steps 2 and 3 for each pattern.
5 - Click Save .
To define floors, please refer to Floor Definition.
The enrolment button is used to send an “enroll me” request to EntraPass with the controller status which includes:
• IP address
• How it is powered (PoE or 12 VDC)
• Full Status
1 - The installers press the enrolment button.
2 - The controller then sends information for a period of 10 minutes at 30 seconds intervals.
3 - Once the 10 minutes delay is expired, the controller stops sending information.
For the enrolment process to be allowed for a given operator, it must first be enabled in System/Security Level/Devices/Connection/enrolment.
When an enrolment request is received, a circled digit will be displayed at the bottom right side of the workstation main window. The digit indicates the number of unassigned controllers. When there is only one unassigned controller, double-click on the circle to open the enrolment Wizard. Follow instructions on the screen. You can also do a right-click on it to display a contextual menu that contains the following options:
○ Define: Display the enrolment Wizard.
○ Full Status: Displays the full status window. Provide a pop-up box with the IP address, how it is powered (IP or 12 VDC) and the full status information.
○ Delete: Remove the selected controller from the list.
○ Assign to an account.
When EntraPass receives data from the KT-1 enrolment process it adds the controller to the controllers unassigned list. The "Controller was added to the unassigned list" event is then generated with the following parageters:
• Gateway description
• MAC address
• Device type
The unassigned controllers list displays:
• Date and time (when it was added to the list) of the gateway
• Controller model
• MAC address
• Serial number
• Broadcast received IP address
The unassigned controller list can have a limited number of 100 entries.
When the video gateway or video vault receives an outbound connection, it receives the following incoming information from the DVRs:
• Name
• Serial number
• IP address
The above list remains in wait mode, ready for assignment to a hattrix account or a defined Corporate Edition, or Global Edition system. In the workstation, the enrolment pending count displays on the lower right section of the status bar. Double click the enrolment pending label to open the following report:
| Column | Description |
|---|---|
| Request date | Date request received. |
| Account | Identifies if the account is selected or assigned. |
| Icon | Video server. |
| Model | exacq model. |
| MAC adress | MAC address of the DVR unit. |
| Request received from | IP address of the DVR that sent the request. |
When you select an enrolment, double-click the enrolment to bring up the context sensitive menu. The following options are available:
| Column | Description |
|---|---|
| Define | Opens the Video Server window that EntraPass pre-populates with information received from the outbound connection, which is the active account. Rename the DVR and save it. |
| Delete | Prompts to confirm and remove the unit from the list. |
When you define a DVR using enrolment, the Video Server window opens, with fields pre filled with information received from the outbound connection. When you define a DVR unit, EntraPass removes it from the list.
If you input the incorrect log in credentials, an error message is displayed. If the import is successful, a confirmation window is displayed. When you click the Save button, the camera details are automatically called. You can then rename the DVR in the Server Parameters tab. To maintain the name of the imported cameras, select the Override Camera name from DVR check box, if you clear the check box, operators can change the name of imported camera.
Follow the steps in How to setup the ioSmart to add an ioSmart reader.
When a controller is disconnected from the server, the controller buffer starts collecting the controller’s events. When the buffer is full, it transfers the oldest events in a secondary buffer (50 to 100 bytes) that always contain 50 events. When the communication is restored, the system then starts sending messages to the Desktop Message List to indicate that the buffer is full and that events are being deleted from the buffer.
• The controller will delete messages in FIFO order (First In, First Out). The oldest message will therefore be deleted first.
• When the controller is reconnected to the server, the controller events will be sent to the Message list all at once, in the following order: events in the controller’s secondary event buffer; a single Event Buffer Overflow will display, followed by the list of events generated while the controller was disconnected from the server.
For more details about the Comment entry box, please refer to Comment Field.
See Also...
EntraPass Gateways
Connection Configuration
Floor Definition
Note